Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
event-as-promise
Advanced tools
Handle continuous stream of events with Promise and generator function.
Instead of listen to event just once, event-as-promise
chose an approach to allow listening to the same event continuously. And we support generator function to enable for await (const data of eventAsPromise)
loop to handle event indefinitely.
We moved default imports to named imports:
- import EventAsPromise from 'event-as-promise';
+ import { EventAsPromise } from 'event-as-promise';
We removed options: { array: boolean }
, to receive all arguments from Node.js event emitter:
- target.on(eventAsPromise.eventListener);
+ target.on((...args) => eventAsPromise.eventListener(args));
Only eventListener
is bound to the instance of EventAsPromise
. Other functions (one
and upcoming
) are not bound and will need to be call in the context of EventAsPromise
. If you want to call it bound:
const eventAsPromise = new EventAsPromise();
- const one = eventAsPromise.one;
+ const one = eventAsPromise.one.bind(eventAsPromise)
button.addEventListener('click', eventAsPromise.eventListener);
await one();
This sample code is converted from Node about page.
import { EventAsPromise } from 'event-as-promise';
import http from 'http';
async function main(ready) {
const server = http.createServer();
const listeningPromises = new EventAsPromise();
const requestPromises = new EventAsPromise();
server
.once('listening', listeningPromises.eventListener)
.on('request', (...args) => requestPromises.eventListener(args))
.listen(3000);
// Wait for "listening"
await listeningPromises.one();
// Loop indefinitely, using generator
for (let requestPromise of requestPromises) {
// Wait for "request"
const [req, res] = await requestPromise;
res.statusCode = 200;
res.setHeader('Content-Type', 'text/plain');
res.end('Hello World\n');
}
}
main();
Handling event in a Promise may not reduce complexity. But it will be beneficial for redux-saga
when mixed with call
effect.
In this example, when the user is connected via CONNECTED
action, we will keep the user posted about file changes, until a DISCONNECTED
is received.
saga.run(function* () {
yield takeLatest('CONNECTED', function* (action) {
const watcher = fs.watch(action.payload);
const changePromises = new EventAsPromise();
watcher.on('change', changePromises.eventListener);
for (;;) {
const changes = yield race([
call(changePromises.one),
take('DISCONNECTED'),
]);
if (changes) {
yield put({ type: 'CHANGED', payload: changes });
} else {
break;
}
}
watcher.close();
});
});
You can retrieve multiple Promise objects before the event is emitted.
const emitter = new EventEmitter();
const countPromises = new EventAsPromise();
emitter.on('count', countPromises.eventListener);
// Retrieve multiple future Promise before the actual event is fired
const promise1 = countPromises.one();
const promise2 = countPromises.one();
const promise3 = countPromises.one();
emitter.emit('count', 1);
emitter.emit('count', 2);
emitter.emit('count', 3);
await expect(promise1).resolves.toBe(1);
await expect(promise2).resolves.toBe(2);
await expect(promise3).resolves.toBe(3);
Same as event listener, if
one()
is not called before the event is emitted, the event will be lost.
Instead of futures, you can use upcoming()
to get the Promise for the upcoming event. Futures and upcoming Promises are independent of each other, as shown in the sample below.
const emitter = new EventEmitter();
const countPromises = new EventAsPromise();
emitter.on('count', countPromises.eventListener);
const promiseOne1 = countPromises.upcoming();
const promiseOne2 = countPromises.upcoming();
const promiseOne3 = countPromises.one();
const promiseTwo = countPromises.one();
emitter.emit('count', 'one');
emitter.emit('count', 'two');
await expect(promiseOne1).resolves.toBe('one');
await expect(promiseOne2).resolves.toBe('one');
await expect(promiseOne3).resolves.toBe('one');
await expect(promiseTwo).resolves.toBe('two');
const promiseThree = countPromises.upcoming();
emitter.emit('count', 'three');
await expect(promiseOne1).resolves.toBe('one');
await expect(promiseThree).resolves.toBe('three');
Note: after the current
upcoming()
has resolved, you will need to callupcoming()
again to obtain a new Promise for the next upcoming event.
Like us? Star us.
Want to make it better? File us an issue.
Don't like something you see? Submit a pull request.
[2.0.0] - 2024-06-02
import { EventAsPromise } from 'event-as-promise'
options: { array: boolean }
, to receive all arguments from Node.js event emitter
target.on((...args) => eventAsPromise.eventListener(args))
FAQs
Handle continuous steam of events in Promise fashion.
The npm package event-as-promise receives a total of 6,375 weekly downloads. As such, event-as-promise popularity was classified as popular.
We found that event-as-promise demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.